Service Manager

About Making Database Schema Changes for Large Business Object Tables

In the production instance of the tenant, we do not recommend making database schema changes (such as creating new fields or changing the data type) to business objects that have a large number of records. This can cause the application to slow down and potentially not respond to regular Service Manager users.

To protect the application from this, you cannot make database schema changes in the production instance of the tenant to business object tables that contain a large number of records. If you try to make the change directly in the production instance, the application displays an error message stating that "The table_name table contains a large number of records. Schema changes cannot be done now." The schema changes are not made.

Instead, makes the changes in the staging instance of the tenant and follow the lifecycle process, via the Service Manager Operations Console. Add the fields in the staging instance of the tenant first (with a smaller number of records in the table), and then use the Service Manager Operations Console to transfer the corresponding fields into the production instance of the tenant.

See the Operations Console Guide for Ivanti Service Manager for information about using the Service Manager Operations Console.

Changing the Timeout Value for DDL Queries

When you make database schema changes in the Configuration Console, you have 30 minutes before the application times out. You can change the timeout value.

If this parameter is missing or set to less than two minutes, the application reverts the value back to 30 minutes.

To change the timeout value, do the following:

1.Open the \AppServer\Web.config file with a text editor, such as Notepad.

2.Navigate to the following code:

 

<appSettings>

<!-- DDL query execution timeout in seconds -->

<add key="DDLQueryTimeout" value="1800" />

</appSettings>

 

3.Change the value of the DDLQueryTimeout parameter. This parameter is specified in seconds.

4.Save the file.

5.Perform a Microsoft IIS reset.